-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include frontend with oss query-service #7247
base: main
Are you sure you want to change the base?
Conversation
Welcome to the SigNoz community! Thank you for your first pull request and making this project better. 🤗 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Looks good to me! Reviewed everything up to bcd62bc in 1 minute and 0 seconds
More details
- Looked at
14
lines of code in1
files - Skipped
0
files when reviewing. - Skipped posting
3
drafted comments based on config settings.
1. pkg/query-service/Dockerfile:27
- Draft comment:
Ensure the target directory exists before copying. Docker often creates it, but explicitly creating the directory may improve clarity. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
- Docker's COPY command automatically creates target directories if they don't exist. 2. Creating directories explicitly is not a common practice in Dockerfiles unless there's a specific permission/ownership requirement. 3. The comment starts with "Ensure that..." which violates our rules. 4. The comment doesn't point out an actual problem - it's just a style suggestion that doesn't improve functionality.
The comment might have merit if there were specific permission requirements for the web directory that needed to be set before copying.
Even if directory permissions were a concern, they could be set after the COPY command. The current approach is standard Docker practice.
Delete the comment as it starts with "Ensure that...", doesn't identify a real problem, and suggests an unnecessary change to standard Docker practices.
2. pkg/query-service/Dockerfile:26
- Draft comment:
Document that copying the frontend build fixes the missing web directory issue (feat(ee): serve frontend pages with query-service #6696). - Reason this comment was not posted:
Confidence changes required:0%
<= threshold50%
None
3. pkg/query-service/Dockerfile:27
- Draft comment:
Consider adding a permission adjustment (chmod/chown) for /etc/signoz/web/ if query-service needs non-root access. - Reason this comment was not posted:
Confidence changes required:33%
<= threshold50%
None
Workflow ID: wflow_TddtpkEENbEBXcjD
You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet
mode, and more.
Hi @davispuh, Apart from the changes mentioned here, we also need to change the corresponding github workflows for this to happen. We are in the process of revamping our CI and we plan to undertake this there itself. |
Summary
#6696 updated
ee/query-service/Dockerfile
but didn't updatepkg/query-service/Dockerfile
This causes
query-service
fail to start when usingoss
tagged images.Workaround is to pass
SIGNOZ_WEB_ENABLED=false
env but it's not obvious because previously it just worked.Related Issues / PR's
Screenshots
NA
Affected Areas and Manually Tested Areas
Important
Fixes
query-service
startup failure by including frontend directory inpkg/query-service/Dockerfile
.pkg/query-service/Dockerfile
, addedCOPY frontend/build/ /etc/signoz/web/
to include the frontend directory in theoss
tagged images.query-service
due to missing frontend directory when usingoss
tagged images.SIGNOZ_WEB_ENABLED=false
is no longer necessary.This description was created by
for bcd62bc. It will automatically update as commits are pushed.